fix destroy so incoming module vars get set

I ran into this while testing out a destroy while giving a variable to a module which then informed a count. If anything was referring to that count as well, it also was blowing up for not finding the attribute. But setting the incoming module vars fixes it.
I was running into some weirdness that was tied to this line. By changing it to an unknown variable value, it would work. 

However, looking at it now, it might be that this was masking some other issue. 

I'm going to poke around and try to fix that. I'll revert this out of the PR.