Storing MaverickContext in request causing issues with portal processes

I just tried to make the switch from version 2.1.1 to 2.1.2 and ran into the following issue.
 
The direct issue is that I have a portal screen which uses Sitemesh to pull in all the content configured to show to the user.  All the content is rendered thru maverick controllers.  The problem now is that under 2.1.2 only the first controller called is rendered to completion, all the rest, resulting in the XML being dumped to the screen.  The root of the issue is the way org.infohazard.maverick.Dispatcher sets the MaverickContext in a request attribute, and if present reuses it.  Since the same request is used and passed along to each controller, the first one sets the MaverickContext and the others use the context from the first.
 
Exactly what situation was trying to be solved by this change.