On the AMQ dev mailing list we have talked about a new issue.
I found out that using the camel-example-management, which has an embedded AMQ broker and using Camel with the VM transport to produce/consume messages, then there is mbean issues.
It works fine in AMQ 5.10.0. But is wrong in AMQ 5.10.1 and 5.11.0.
See the attached screenshots.
Notice how the mbean tree for dynamic producers keeps growing for 5.10.1 and 5.11.0.