Unfotunately, that doesn't seem to be the problem - the same result is returned with or without gems required. Other gems actually work as I would expect them (as far as the load path updates are concerned) - i.e.:
#require 'rubygems'
#require 'watir'
require 'capistrano'
puts $LOAD_PATH
>ruby watir.rb
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-ssh-2.0.2/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-ssh-2.0.2/lib
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-sftp-2.0.1/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-sftp-2.0.1/lib
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-scp-1.0.1/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-scp-1.0.1/lib
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-ssh-gateway-1.0.0/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/net-ssh-gateway-1.0.0/lib
c:/dev/ruby/lib/ruby/gems/1.8/gems/highline-1.4.0/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/highline-1.4.0/lib
c:/dev/ruby/lib/ruby/gems/1.8/gems/capistrano-2.4.3/bin
c:/dev/ruby/lib/ruby/gems/1.8/gems/capistrano-2.4.3/lib
c:/dev/ruby/lib/ruby/site_ruby/1.8
c:/dev/ruby/lib/ruby/site_ruby/1.8/i386-msvcrt
c:/dev/ruby/lib/ruby/site_ruby
c:/dev/ruby/lib/ruby/1.8
c:/dev/ruby/lib/ruby/1.8/i386-mswin32
.
>Exit code: 0
The different output I referred to earlier with watir (it's no longer returning the error originally reported) is a duplication of the standard ruby load path:
#require 'rubygems'
require 'watir'
#require 'capistrano'
puts $LOAD_PATH
>ruby watir.rb
c:/dev/ruby/lib/ruby/site_ruby/1.8
c:/dev/ruby/lib/ruby/site_ruby/1.8/i386-msvcrt
c:/dev/ruby/lib/ruby/site_ruby
c:/dev/ruby/lib/ruby/1.8
c:/dev/ruby/lib/ruby/1.8/i386-mswin32
.
c:/dev/ruby/lib/ruby/site_ruby/1.8
c:/dev/ruby/lib/ruby/site_ruby/1.8/i386-msvcrt
c:/dev/ruby/lib/ruby/site_ruby
c:/dev/ruby/lib/ruby/1.8
c:/dev/ruby/lib/ruby/1.8/i386-mswin32
.
>Exit code: 0
^^ That's just weird.
I'm new to development and therefore (obviously) new to ruby - as such, I've appreciated the feedback!
Matt