timeout on connection that is not writable does not cleanup on primary

If an incoming socket from a backup is not writable at the point it times out, then the sessions get cleaned up but the connection observers are not notified of the closed connection (as the code used by the io layer is not yet deleted; it is only deleted when the socket is writable).

For the primary in an ha cluster this means it does not fully handle the lost connection.