My hosting company verified that the cookie in question was being added by their load-balancing appliance. It has nothing to do with the IIS server.