Memory Leak Bug in V8?

With node.js .10.2 I ran into a memory leak that (kinda) makes sense but I believe its a bug. What do you guys think?

function Go(foo)
{
  var someArray = [];
  fillArrayWithLotsOfStuff(someArray);
  doSomethingWithArray(someArray,
   function(){
     setTimeout(function(){Go(foo);},0);
  });
} 

If I move the declaration of someArray to a higher scope the memory leak is gone (for the most part). The leak is happening because the closure created by setTimeout maintains a reference to someArray when its in the function scope. The closure itself is never garbage collected either so there's still a leak though much smaller. Its as if this is recursion but its not. Yeah, Go is going to be called from within itself but it returns immediately so, IMO, the previous instance should be cleaned up.

This can be rewritten to accomplish the same thing with no leak at all. Its not a problem for me, just a topic for discussion...

Edit: Modified code sample. Forgot that setTimeout was provided an anonymous function. That makes all the difference.