Service workers are a lot "stickier" than that. If you think about it, they are all about caching. A service worker activation could count as a cookie itself since it can modify future requests, and if you modify the requests in a way that it emulates a cookie being set then it is a cookie.
Surely service worker https requests are bound by the exact same cookie rules as any third party script, resource, etc?