Query behaviour on first Logon message from initiator when disconnected during session expiry

[I searched to see if this had come up before, but couldn't find it - many apologies if this is a duplicate]

We have an issue when an acceptor receives the a Logon(A) message to start a new session from an initiator which was not connected at the time that the old session expired.

The Logon(A) message has 34=1 and 141=Y, so I would expect the acceptor to just go ahead with the new session. Unfortunately the logon message is being passed to Session.next(Message), which is getting false from a call to checkSessionTime() and so just calls Reset(), which sends a Logout(5) message (without having reset the sequence number) and disconnects (without even waiting for a Logout(5) response).

Our applicaiton is based on a slightly-customized version of QuickFIX/J (currently based on 1.0.4), so upgrading to a later version to see if this is resolved is not a quick and simple task, hence I thought I'd just ask a) if this is/was a known problem, and b) whether upgrading will resolve it before I investigate further next week.