Been covered quite well before--new features have new policies that get adjusted more often while it's all new and as new things come up. It gets more stable with time as more cases are covered and decisions are better thought out. It's been like that pretty much since the beginning so nothing new or surprising there.
You say that like its acceptable when its not. My guess is that no policy changed at all. The screw-ups who where in the way have been removed.
No developer should have to guess at what is acceptable. They should be told with supreme clarity why the app was pulled and in absence of that clarity, the app remains available.
----------
I'm not saying they were right in this case (actually the revised policy means they probably were wrong) but there are at least two reasons for that: security and influence on user's experience.
Apple basically don't want developers to mess with those aspects.
The point is Apple should indicate the exact issue and not leave it to speculation. Developers follow rules. If Apple cannot articulate a violation then one does not exist.