Noticed the same thing. Burns 10-20% in both IE on Windows 8.1 and Edge on Windows 10. Chrome is better, but still runs 5%+ when nothing is going on. Have to close the app in order to bring CPU usage back down to normal. Definitely worth fixing, as a web client really shouldn't be burning CPU time at all when idle.