That is right, that only covers the case when the client restarts. Otherwise, in case when there is just a connection loss, the problem is that there may be multiple connections and queue redundancy, so the loss of a single connection would not necessarily mean that the connection to the queue is lost. What is needed here is a callback API for queue connect/disconnect events that would fire an event when the connection to the queue is completely lost, as well as when a connection to the queue is established.
There is some internal API that may be of help, but you'd have to do a lot of bookkeeping yourself--it would be pretty complicated.
Another option is to implement a queue "pinger" yourself, in your client, by periodically putting a special object into the region backed by the queue, which would cause the server to respond by putting a response object on the queue, on which the client would have registered interest.