I don't like it, that's catching any exception. It would also make web2py slower on the cases where that exception is being thrown consistently on every request, of course that will only happen to Apache users but, still, it looks a lot like hiding a bug.
Why won't Apache just die...
It also appears that this problem only starts happening when you have more than one web2py running in the same apache server. The solution for them is to use different process groups (or really just stop using Apache).
As Fabrice suggested here:
This really really looks like a bug with Apache/mod_wsgi, possibly only on microsoft windows, it doesn't happen in any other configuration I've tried.