What sets this one apart from the other two (all other factors being equal) is the clearer descriptions of the principles, and the checklists. I also like the way that the author goes deeper into details about how to align the WBS to various project types (product-, service- and results-oriented projects), and the more complete life cycle view that this book provides. As an aside, a results-oriented project, previously mentioned, is a project such as organizational change management, which doesn't produce a tangible deliverable in the same manner as, for example, a software development project does.
To put into context the comparison among the three books, I favor this one because of personal preferences. Each merits, in my opinion, equal value, and any of the three will give you the knowledge necessary to develop a work breakdown structure.