Get rid of __future__.with_statement.

Moving to Python 2.6 only means that we can rely on the 'with' statement being
present.

Reviewed at https://reviews.reviewboard.org/r/6576/