We confirm this issue, it has to do with the new ajax rerender method, introduced in 2.1, it should be fixed very soon. we never risked so much in a develop/beta version, but this time we had to since this means a notorious increase of performance in ajax render methodology.