It sounds like it sticks kernel objects if the same type in one big pool, whereas they used to have per container pools. That'd lead to better utilization and probably better caching behavior too although that's not explicitly stated.

The big challenge would be making sure that the different containers' resource limits are respected, but it looks like they're addressing that head on.