Got the same problem at a colleague's desk. He was working with JBoss AS (4.2.3).
Solved it by stopping the server, removing the cached deployment data at server_dir/tmp and server_dir/work and started again.
JBoss often gets confused in older versions when the same deployment unit has been redeployed several times.