No, when you use the wrapper in the Sharp Develop IDE the error does not occur, that's because if you run the program from sd, it will run in its own process, when you close the program window, that process ends (and everything gets cleaned up).
If you run the program from b4p it runs in the same process as b4p, so when you close the window, the b4p process still runs. That's were the issue probably comes from(I read somewhere, that XPCOM components can't stop and restart in the same process, so that might explain the error on the second start)
I don't have any experience with this, there might be a way to handle all this alot better in the wrapper, but I don't know it.
This shouldn't cause any long term problems for windows, it should all get cleaned up when the b4p process is closed.