Initiator's application.onLogout() is not called if Acceptor connection is forcibly closed

Set up two QuickFIX/J applications (one as acceptor, on as initiator) and connect them together, then terminate/kill the acceptor application (i.e. as if it had crashed) - the inititator application gets the "Disconnecting" event but its implementation of application.onLogout() is not called

Diagnostic investigation suggests that Session.disconnect() is not returning from the line

responder.disconnect();

Terminating the initiator application in the same way doesn't have the same problem - the acceptor gets the "Disconnecting" event, followed by a call to its implementation of application.onLogout() as expected.

I tried re-building both applications on QFJ 1.0.2 and doing the same tests; this seems to work OK for both sides, so I guess something's changed between the two releases.