Node HTTP integration memory leak #8129

From slack: https://sentry.slack.com/archives/C28MX5WAJ/p1684166405392469

I have a customer reporting memory leaks specifically with node's http integration. They mentioned it occurs when they specify tracingPropagationTargets. I'm wondering if it could be tied to this line? Perhaps in a scenario of raw urls with many different combinations of params?