If you're sending a message from one EAR to another using user objects serialized, thats true. I guess in this case, we should ensure that the tcp protocol is used to ensure data is serialized into and out of each EAR/class loader.
We should reserve the VM transport for use cases where publishers and consumers are in the same class loader - will add warnings to the website to this effect.
I would suggest in-classloader and in-vm protocols - going to TCP just to force serialization seems like a lot of overhead compared to just serializing to a byte array.
