I don't like the proposed syntax though, because it introduces a new meaning for the & operator. In all other uses, the & operator modifies the type of the operand, to be the opposite of the * operator.
In the proposed syntax, & becomes something a little bit different: a C++-style reference. I think it would introduce too much language confusion.
A more C-like syntax would be:
defer(captures-by-value; captures-by-reference) {}.
Defer() statements would be executed at scope-exit, in last-in first-out order. Standard block scoping would apply for anything declared inside of the defer().