Has this issue also been reported in the JIRA for JBoss?
I am running into it now as well and couldn't find any information about
this in the releasenotes for 4.0.3.SP1
There is no reason why the release notes would discuss a log4j version we have not tested. This seems to be an issue of including the log4j.jar in the war and having class loader conflicts. A bug report with the full description of the deployment causing the problem is needed.