We figured out what this is about. The exception you're getting is actually not a real license exception but is caused by some incorrect initialization in the server. It SHOULD only happen if you have set a default timezone in your project BEFORE you ever succesfully ran your project in the latest 3.0. You can fix it by removing the default timezone, deploying and then setting the default timezone again and redeploying. We will fix this in the next version.