When an application uses a remote EJB3 interface the call is serialized and deserialized. While mandated by spec this is unnecessary if the EJB is running in the same JVM as the calling client. Having the option to skip serialization would bring JBoss inline with other major JEE vendors. Performance tests on a transactional application that has all business logic in stateless session bean methods is showing 20% cpu overhead just for the serialization. Having 20% more production CPU capacity is more important than claiming strict EJB3 compliance. JBoss AS response times are better too.