To add to the weirdness:
If I then hot redploy the EAR file after things fail the first time, the WAR successfully deploys. If I shut down JBoss and restart it, the deployment fails again, but succeeds after another hot redeploy. It seems like my WAR file is being deployed before something else it depends on, but then when I hot redeploy, that dependency has been taken care of.
The same thing is happening in 3.2.5 as happened in 3.2.4
This was probably pretty obvious to everyone but me, but removing the "ROOT.war" folder from the jbossweb-tomcat50.sar folder under deploy did the trick - there were probably conflicts because we deploy our application under the root context that this WAR was apparently using