This was fixed in the 3.2.4RC1 release by scoping the web console jars. Download this release to see how it was done as the same setup can be applied to 3.2.3.
Does jbossweb-tomcat50.sar have the same problem since it uses a lot of common jars, such as ant.jar and commons-logging.jar?
I used the management jboss-service.xml as a reference and added this, but it didn't work. Obviously this is not clear to me, and as you can guess I got a ton of exceptions... any advice?