You probably are packaging JBoss related jar files (ex: jboss.jar) in your application. If so, then remove them from your application EAR.
i don't think so, see, our previous jboss config, didn't have default,all. min jboss servers, it simply had pmp.
what i did in jboss 4 is simply rename default dir to pmp, so it contains in its lib directory jboss 4 jars., the ear itself does a huge amount of jars, (hibernate's, jcifcs, commons, velocity, aspectwekz, xom, jxapth, spring) but i'm not sure if it contains jboss jars as well, (do all jboss's jars, begin the word jboss?)
funny thing, (ok, it's not funny, it's depressing) i tried copying the ear, to jboss 3.2.8 sp1, even that didn't work, becouse then hibernate started complaning our hbm files were not correct. it claimed that an attribute "select-before-update' must appear in joined subclass element, even though it doesn't have to be, i suspect it might be due to xml parser, being somewhat different, i thought at first it might be becouse xerces is present in endorsed lib of jboss's lib (giving it precednce over java's lib) but removing them, or taking the ones from jboss 3.2.5 didnt' help.
our ear only works jboss with 3.2.5.
i have a little update on that, there were jboss jar in the ear itself, i removed them all, but it didn't help, but now i'm thinking it may be the removeHome at fault becouse if see another NoSuchMethodException on commons logging cannot find setter method on BaseModelBean.
problem is i cannot use commons logging that came with jboss as our application uses it's own commons-loggin(1.0.4) with constructor in log4jlogger which does not appear in commons-logging jar of jboss