I guessed that the ASP.NET ExecutionTimeout would have an effect on my IIS-hosted WCF service, however, it does not.
Is there some magic going on in WCF which disables the ExecutionTimeout?
I've found out that since .NET 3.0 SP1 WCF disables ASP.NET's ExecutionTimeout
by setting the timeout to an infinite value. Therefore, only WCF-specific timeouts apply.