We also have the issue on a hosted version 2.5.0B6. Some users have complained. Hopefully next release will solve it