If a non-durable JMS subscriber gets disconnected then the underlying temporary queue should be removed so I think that part is probably a bug. I'd recommend attempting to reproduce your issue on the latest release (2.2.14.Final is pretty old at this point).
Aside from that, we recently implemented https://issues.jboss.org/browse/HORNETQ-1383 which may interest you.
Thanks - we'll start upgrading. The slow consumers feature would be great for our multi-queue address with fast consumers. Do you know when we should expect another official release? (If it's within 60 days, we'd just wait for that)
I'm not sure when the next official release will be.