Don't try to re-resolve module

I discovered a bug in meteor-require, in the case where a dependency was resolved in the process of resolving another dependency. This led to require trying to resolve said dependency after it was already removed from waitingModules, resulting in accessing an undefined object. See line 63 of my branch.

I'd write a test for the case if the package had a test suite.