I am not sure if it is a problem or OK. I found a Stack Overflow question and my answer on answerspice.com.
http://www.answerspice.com/c119/1546863/wcf-in-iis-6-server-cannot-set-status-after-http-headers-have-been-sent
WCF in IIS 6: Server cannot set status after HTTP headers have been sent
Edit:
Based on the answers below, it looks like they may be breaking the rules. Is it possible to do anything about it?
Edit2:
Now also on FriendFeed:
http://friendfeed.com/lubos1/45613ea3/wcf-listenbacklog-and-maxconnections-can-t-be
Edit3:
Now also on tuts9.com:
http://tuts9.com/questions/50063/why-doesnt-my-wcf-endpoint-throw-a-max-clock-skew-exception
Why doesn't my WCF endpoint throw a Max Clock Skew exception?
Edit4:
Found another one:
http://efreedom.com/Question/2-147000/Remotely-Chrome-IE-Page-Loads-60seconds-Firefox-IE-Local-Machine-Instantly
Edit5: And another
http://www.questionhub.com/StackOverflow/3372175
The interesting thing here was that this was the first link in a google search. The original article was not on the first page.
Edit6: And another
http://www.comanswer.com/question/wcf-chunking-streaming-make-it-transparent-for-client