Try moving your Wicket classes (as an experiment) out side of your WAR. Put the jars in, say, domain1/lib/ext.
See of that changes the behavior at all (those will be loaded by the overall server classloader, and not be specific to your application.
Not optimal in terms of packaging, but may give an interesting data point.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=277109