I don't know that it so much that the essential complexity is being pushed into the global state - a global constraint, for example, is global regardless of how you implement the system - but factoring into tiny modules puts more layers below that level. That is not the wrong way to do things, but it has not gotten rid of the complexity.

And using only small classes and methods does not guarantee the elimination of accidental complexity either; I have seen enough cases where the code has become a sort of shell game, were you go from class to class looking for where something actually gets done. As a rule of thumb, code with classes having 'helper' in their names probably has this problem, though it would usually be easy enough to rename them to conform to the single-responsibility principle.