F5 not closing inside connection when outside connection dies

Greetings!

I have a VIP that doesn't close the inside connection after the outside connection dies. Open a connection and login to the app, 3 to 5 connections will show up in the connection DB. If I close my laptop the connections start to die as you would expect. However at some point the last frontend connection dies but it's related backend connection never dies. The pool member seems to have a keep alive that runs, but why doesn't the F5 close that connection anyway? I guess the real question is, is there a setting somewhere like in the tcp profile to say if one side of the connection dies, timeout the other side in a X seconds.

Thanks as always!

Joe