web service runs after calling ASPX page is closed

I have been racking my brain trying to figure this one out, so any ideas would be appreciated!!

I have been working on a web service. From the web service call, queries are executed and update sql's are executed. The test aspx page that calls the web service is just looping through a ton of records and calling the web service in a loop over and over. When I close the web page, the web service is obviously still running because I can open up Sql Profiler for Sql Server 2000 and see queries still getting launced. I can use Query Analyzer to see the number of non null values for a field in the table that gets updated and it keeps going down (and since the update sql from the web service is setting this field to a non null value, it must still be running).

Is this normal or am I missing something? Is there a way to control this? I'm worried about our application going into production and many users abandoning their browser session yet the web service and sql server keep on working eating up valuable resources.

Thanks for any thoughts and I can post code if that would help.This is normal behavior.

Inside the ASPX page, you can check to see if the client is still connected with Response.IsClientConnected.

Be very careful, however, because on IIS 5.0 this check needs to make an out of process call, which could end up hurting performance. You'll need to do some measurements of your application.