If I hijack JMSQueueService, and attempt to bind the queue as queue/foo/bar/baz/tacos/someQueue, it may work the first time, but subsequent created queues end up with a duplicated section in the resulting path. Trying to bind to queue/foo/bar/baz/gouda/anotherQueue might result in queue/foo/bar/baz/tacos/gouda/anotherQueue.

Seems some stack doesn't get completely popped when HornetQ goes creating parent contexts in order to plant the leaf resource.