default scoping and associations

Consider the following:

class User < ActiveRecord::Base
  has_many :friends,
           :foreign_key => 'user_id',
           :class_name => 'Friendship'
end

User.scoped(:conditions => "id != 7").find_each do |user|
  p user.friends
end

The result is:

User Load (1.0ms)  SELECT * FROM users WHERE (users.id >= 0) AND (id != 7) ORDER BY users.id ASC LIMIT 1000
User Columns (5.0ms)  SHOW FIELDS FROM users
User Load (0.0ms)  Mysql::Error: Column 'id' in where clause is ambiguous: SELECT users. FROM users INNER JOIN friendships ON users.id = friendships.user_id WHERE (friendships.friend_id = 1) AND (id != 7) ORDER BY users.id ASC LIMIT 1000
ActiveRecord::StatementInvalid: Mysql::Error: Column 'id' in where clause is ambiguous: SELECT users. FROM users  INNER JOIN friendships ON users.id = friendships.user_id    WHERE (friendships.friend_id = 1) AND (id != 7)  ORDER BY users.id ASC LIMIT 1000

Ignoring that I could have specified "users.id" - I used that example to show an error. Isn't it a bit strange for the current scope of the find_each to carry through to associations? Imagine something more exclusive like:

User.males.find_each do |user|
  p user.female_friends
end

That would find nothing and not raise an error!