Hi Brett,
Its not fixed in 4.3.0.final

All the code snippets listed above are as is in 4.3.0.final as well. hence all the comments/testcases listed on this bug are valid even in 4.3.0

Thanks