Oh there's a bonus too =)

In brief: because of the way [__call](https://github.com/cakephp/cakephp/blob/3.0/Cake/ORM/Table.php#L1042-L1047) is defined in Table, a behavior (or rather _any_ two behaviors + the table) cannot implement `foo` and `findFoo` without making `$Table->foo()`  ambiguous. Hmm just realized also `$ATable->all()` would call a behavior's `findAll` method, if implemented, [before the table's own `find('all')`](https://github.com/cakephp/cakephp/blob/3.0/Cake/ORM/Table.php#L1032-L1034) - [always](https://github.com/cakephp/cakephp/blob/3.0/Cake/ORM/Table.php#L583)... don't think I like that.

I discussed this with @lorenzo last night, it will be a good idea to simplify (or alternatively ensure consistent) __call logic -I plan to put a proposal in a separate PR.