You're completely right that this got fixed in ASP.NET 4, but I still think it's a fun read to see how an unyielding tribute to backwards compatibility can have really odd implications.