I got a same problem like you.
The first one have many way to solve:
1. delete the persistence.xml
2. add tag <non-jta-data-sorce /> in persistence unit.
3. add a data-source named CasPersistence
But the second one I still have no idea about it until now.
In other discuss, someone says that delete the following file in the war file:slf4j-api-1.5.8.jarlog4j-1.2.15.jarslf4j-log4j12-1.5.8.jarI have tried too. After delete these jar files, the deploying process will halt on loading log4j configuration (log4j.xml), still can not deploy.To solve these problems I suggest that you should deploy the CAS old version 3.3.5(.1) or deploy on the JBoss4.The conflict just happen on CAS 3.4.x with JBoss5.x (or newer)