I get this same behavior in JBoss 3.2.6 with the EJB classpath. I don't have a war so can't confirm the WAR classpath behavior.
Then this should be JBOSS's problem, As the order of its class loader is not properly.
Is it correct?
Any solution of this problem?