stomp+nio leaking file descriptor on client drop

The bug is observed on code checkout from https://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.0
A server is initiated with stomp+nio transport on port 61612.

A client connects. A SelectorWorker is created on SelectorManager:68.
If the client drops the connection an exception is received at StompNIOTransport:91.
"java.io.IOException: An existing connection was forcibly closed by the remote host".
But selector are not cleaned up. It works with stomp transport. But not with stomp+nio.

What I see in the end is an increasing number of "connections" if the JVM.