I think this is such a common pitfall, at least in part, because a person writing a tutorial about OO needs to mention and explain inheritance and so also feels compelled to explain the "power" and "benefits" of inheritance. The pitfall is going on and on about the benefits, rarely even mentioning the pitfalls, and using really sucky examples to explain all of the things that can be done with inheritance.

Though I'm often quite disappointed that tutorials on OO nearly fail to mention data organization, data hiding, and associating the code with the data it works on. Those are the big wins of OO for me.