That is indeed the modern behaviour of chroot. It is not clear that the "original implementation" shown in the article shares that property, though.
EDIT: That's not to say it doesn't prevent that behaviour. If the usual code to prevent you ..ing above the root checks against u.u_rdir instead of /, it might well work as modern implementations do.