Can you try 2.1.2CR2, as the current trunk (and that release) no longer uses ContextualHttpServletRequest for wicket pages. Also your comment
touches request parameters (at least to restore conversation useless in wicket environment)is not valid, because we do support conversations in wicket, including propagating them via request parameters.
Ok, some people think that Seam conversations are useful with Wicket, some don't. It is just an opinion.
From my perspective conversational context is useful. But I prefer to implement it as a typesafe class instead of Map<String, Serializable>. Therefore I find Seam implementation of conversation context useless.
I have to be honest. I use SMPC which is tied with Seam conversations to avoid LazyInitializationException. But it is until I find an appropriate alternative.