There are zillions of places ASP.NET can cache stuff...okay maybe not ZILLIONS, but 5, 6..9? Code can be cached on the server or at any server in between, as well as your browser, it can be cached in the Session Object, the Application Object, and, uh, you'd think I'd remember this better...!
So it could have been a caching issue, just not in your browser cache.
Cheers,
pigpen
