It didn't support in-VM optimizations in your example.
It did some extra work to spot the class cast and
reverted to RMI semantics.
Are you using PortableRemoteObject.narrow() for the remote
home? Are you using the ByValueInvoker?
Yes, in 3.2 the only way to get my packaging to work is to use the ByValueInvoker. I use PRO in both examples.
It was also necessary to comment back in the localhost provider in jndi.properties.
It would be cool to include, or document all the steps necessary to create a new configuration called 'compatible'. In this configuration, users would be able to drop their 2.x deployments into.