When using cancel button, models aren't unloaded from VRAM

[BassJMagan]

Expected Behavior

I expect presssing cancel to be the same as having a batch be completed normally, all things unloaded and not taking all sys resources.

Actual Behavior

Pressing cancel leads VRAM for instance to still be 22/24GB VRAM on Flux, and I believe this leads to sometimes when trying to make an image after the s/it shoot waaay up from 2-3 s/it on a 3090 to 10-20s/it or worse. The issue is solved by restarting but very inconvenient if i want to try a lot of diff ideas and queue up generations and want to cancel midway to change prompt.

Steps to Reproduce

Queue up multiple images to be generated, then cancel them all while it's still well into the generation process.

Debug Logs

n/a

Other

No response