Okay so this is a bug which also is a problem for native library (not only support library).
The only workaround I can suggest is to create your own back stack and then handle onBack with your own custom implementation setting the right animation as you go back through your own stack.