IIS 7 Integrated Pipeline Mode Problem

Our ASP.NET apps started to behave weirdly when running on IIS 7. We found out, that switching the IIS mode from Integrated Pipeline to Classic worked well. Lately I've done some debuging and found out, that after calling Response.End() in some click event, the IIS continued to process other events and methods, which included further successful (?!?) writing to the Response object (in our PreRender and Render event). Closing the socket using Response.Close() prevented this :))).

I have thought for all my life, that after Response.End, somebody tries to stop processing the page :).