This issue was indeed present with version 0.4.91, and has been solved with 0.5.2. We used compressed assets, but the engine got a bit overzealous when it came to decompressing the assets into temp storage. If you are on an up-to-date Windows version, they will be automatically cleaned up after some time :)