As per the spec, the .war has its own isolated classloader. However if you want to change that behaviour then follow this http://www.jboss.org/community/wiki/useJBossWebClassLoaderinJBoss5
If not, is there another way of an EJB access a static property inside the Web applications?
If that class with the static field is meant for both war and EJB jar, then why not package that in a separate jar file and place it in EAR/lib folder so that it's available to both the components and loaded by the same classloader.
Creating the jboss-classloading.xml file worked fine but what you said made me think better and it really was my mistake.
The class I was using was placed in both blaces (war an EJB jar) so it was loaded twice.