Looks like you forgot to register the http module with Windsor Castle with IIS7

Try adding it to the system.webServer section as well?

<configuration>
    <system.web>
        <httpModules>
            <add name="PerRequestLifestyle" type="..." />
        </httpModules>
    </system.web>
    <system.webServer>
        <modules>
            <add name="PerRequestLifestyle" type="..." />
        </modules>
    </system.webServer>
</configuration>

It helped me:

<system.web>
  <httpModules>
      <add name="PerRequestLifestyle" type="Castle.MicroKernel.Lifestyle.PerWebRequestLifestyleModule, Castle.Windsor" />
  </httpModules>
</system.web>

I've come across this issue in my dev enviroment. What's worth noting is this tag:

  <validation validateIntegratedModeConfiguration="false"/>

While it obviously does what it says on the tin, it can stop those pesky errors showing up. Assuming the rest of your configuration is working Ok.

What has worked for me:

<system.webServer>
  <validation validateIntegratedModeConfiguration="false"/>
  <modules runAllManagedModulesForAllRequests="true">
    <remove name="PerRequestLifestyle"/>
    <add name="PerRequestLifestyle" type="Castle.MicroKernel.Lifestyle.PerWebRequestLifestyleModule, Castle.Windsor"/>
  </modules>
</system.webServer>

I had the same error, but it caused by another reason:

I tried to resolve IService at Application_Start for custom route class processing, but type for IService was registered with PerWebRequestLifestyle. Routing subsystem stays at higher level that web request, and objects not exist at route processing time.