More grist for the mill - it looks like the IIS application pool is trying to load the assembly in its own isolated domain, which is probably why the call DoCallBackInDefaultDomain is in the stack trace. Since the assembly is loaded in an isolated domain, the framework is trying to serialize an object, which somehow includes the HttpContextWrapper property.
I hope this helps!
I hope this helps!