I've seen this too and think it has to do with KeepAlive options
keeping a socket open.  If the socket is still open and the browser is
closed, However, I've never set out to explicitly check out my theory,
and my latest win build of Ruby 1.8.2 (as of Dec 2004), doesn't seem to
show the error as frequently.