I bet if you look at 3.0.4 you will see that warnin
The only difference is that 3.2.x stops the
deployment on any warnings.
3.0.x displayed the warning and continued.
You can change 3.2.x back to the 3.0.x behaviour
in conf/jboss-service.xml, look for the strict verification
attribute on the EJBDeployer and set it to false.
Better would be fixing your bean class to throw the
same exceptions as the local interface.