Checking obscure serialization bugs during development

Hi all,

There are some application (not wicket!) bugs that occur only when wicket
serializes a page, while the same code works if the page is kept in memory
during subsequent requests.

For instance a == comparison may fail if either side of the expression is
serialized/deserialized.

These bugs often go unnoticed during development since usually the active
page is kept in memory.

So I was wondering if there is a way to force wicket during development to
always serialize pages and never keep any pages in memory in order to make
such bugs more apparent to the developer.

Thanks in advance
Marios