This exception is not related to your war file deployment and if admin console otherwise behaves well, you can disregard it - it is caused by the fact that update client Java API is apparently unable to correctly process packages which contain combined 32 and 64 bit content files when checking for available updates. I'll file an issue for this.
If you find the exception too distracting, you can get rid of it by specifying offline admin console mode - to do that, you need to set this system property in your domain.xml file and restart the server:
<jvm-options>-Dcom.sun.enterprise.tools.admingui.NO_NETWORK=true</jvm-options>
[Message sent by forum member 'snjezana']
http://forums.java.net/jive/thread.jspa?messageID=482123