AnimatorDefaultTransition has been leaked / Setting up transitions on layers and sub sub state machines

I am getting the following warning every few minutes in the console.

Cleaning up leaked objects in scene since no game object, component or manager is referencing them AnimatorDefaultTransition has been leaked 200 times.

I have the Animator Controller open and have setup several Sub State machines on the base layer with non overlapping conditional transitions from Any state. I also setup several additional layers for blending. Some of these layers and sub state machines are place holders and don't have states and transitions setup yet. That should not be a problem in my opinion.

I am also puzzled by three things but I am not sure they are related to the leak warning.

1. the orange "Entry" block being forced to transition on every Sub State Machine and Layer. Why can't this be optional except on the base layer? I want to use the Any State instead. To me this makes more sense to keep a layer inactive when its conditions for blending are not active.. Otherwise I am forced to figure out how to have a state that does nothing on the layer while it waits for when one of its states should be applied. I don't know if leaving the animation not set is the best way to do that. On a sub state machine, I would like it to go directly to the unique conditional state I am seeking rather than do a stop over on default state for the sub state.

2. Is Any State the same State on any Layer and Sub State or does each one have its own?

3. What is the purpose of EXIT on each Layer and Sub State machine? I assume I don't need to transition to these if the animator controller is always running.

4. I am a software engineer and I get frustrated with the documentation in some places, especially when a field is not mentioned or is not described in adequate detail. Tutorials are useful but it can take too long to find what you need and you don't know if you will. Also if I need to refresh myself on a particular field, the manual should be a faster way. An example is found when clicking the settings gear of a layer. There is a field there called Timing. However its not selectable so its probably some future feature. I appreciate good documentation and cross references from places you might land in documentation to where you should be reading. Thanks for what you have done and I hope it keeps improving. I apologize if I have missed some place in the documentation that would set me straight in this problem.