ActiveMQTempDestinations hold onto the source connection that created them. When the source connection is closed, its temporary destinations are deleted. Unfortunately, DestinationInfo commands convey the destination object with its source connection to all other connections on the same VMTransportServer. Hence when these other connections are closed, they attempt to delete the source connection's temporary destination.
Note that enabling marshaling on the VM transport works around this bug because destination serialization and deserialization does not maintain the source connection reference.
This bug was not present in 5.4.2.