HornetQ memory leak when undefined destination is used

Issue

• We have an MDB deployed that we're not using. The MDB is looking for a destination that isn't defined. This appears to be causing a memory leak. We saw 600-800 HornetQ threads spawned resulting in an OutOfMemoryError. Since the destination was added, the thread count has been stable.