I have gotten Spring MVC and Spring Web Flow working with Liferay 6.1 with the changes you guys made to the parent context.
The steps as outlined are as follows:
1) Add the following to the web.xml
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>ViewRendererServlet</servlet-name>
<servlet-class>org.springframework.web.servlet.ViewRendererServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ViewRendererServlet</servlet-name>
<url-pattern>/WEB-INF/servlet/view</url-pattern>
</servlet-mapping>
2) add the file applicationContext.xml to your WEB-INF directory, including imports to your Spring MVC context XML files.
3) add your Spring MVC context configuration XML files anywhere you want, provided the path matches what you have in the applicationContext.xml. I personally prefer WEB-INF/contexts/.
4) modify your portlet descriptor in your portlet.xml file so the <portlet-class> references either org.springframework.web.portlet.DispatcherPortlet or your own class that extends DispatcherPortlet. Also include the init-param "contextConfigLocation" with the value as the path to the spring configuration for that portlet.
5) configure your portlets context configuration XML with the portlet specific settings, such as registering controller beans, view resolvers, flow registries, flow handlers, and portlet mode handlers, etc.
As part of this, the Service Builder script will need to be modified such that the *LocalServiceUtil classes implement java.io.Serializable. Otherwise they cannot be injected into the flows or controllers.
If you want to see some of how this could look, I would check out the Spring MVC and Spring Web Flow scaffolding in MyEclipse for Spring. They use their Spring DSL (which would be an analog to our Service Builder entities) and allow you to scaffold out your app with a variety of view technologies, such as Spring MVC, Spring Web Flow, GWT, Flex, etc.
This will be a great feature addition to Liferay IDE