Reduce amount of spurious exceptions during remoting shutdown

If the remoting is already in flushing mode, and an inbound association arrives, we try to disassociate it immediately -- causing a spurious exception that is harmless, but annoying if the driver has been shut down already.

This fix attempts to reduce the window for that to happen. If someone could just check it and see if it happens again, that would be awesome.