This certainly appears to be a bug, do you have a testcase that we could use to reproduce the issue and raise an issue against AMQ?
attached is a test to reproduce this problem. I described steps needed to run the test in readme.txt. Also sample test output is included.
I'd appreciate feedback on issue created in AMQ jira.
testcase.zip 22.2 KB